Battery pack with supplemental memory

ABSTRACT

Features are disclosed relating to a case for a mobile device that provides supplemental battery power and supplemental storage space to the mobile device. Additional features are disclosed relating to an external storage device that can provide supplemental battery power and/or supplemental storage space for one or more devices. Further features are disclosed relating sharing and searching for files. Files may be shared across multiple (e.g., two or more) devices, operated by or associated with multiple users, providing multiple file storage locations. Files may be searched across the multiple devices using, e.g., search terms, tags, and/or other search options. Searching may also be performed with respect to activities performed in connection with subject files.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional PatentApplication No. 61/909,578, filed on Nov. 27, 2013, and titled “BATTERYPACK WITH SUPPLEMENTAL MEMORY,” and of U.S. Provisional PatentApplication No. 62/019,824, filed on Jul. 1, 2014, and titled “BATTERYPACK WITH SUPPLEMENTAL MEMORY,” the disclosures of both of which arehereby incorporated by reference in their entireties for all that theydisclose.

BACKGROUND

Field of the Disclosure

Various embodiments of this disclosure relate to mobile electronicdevices and/or to wearable computing devices, and certain embodimentsrelate to a battery pack with supplemental memory for use with a mobileelectronic device.

Description of the Related Art

Mobile electronic devices sometimes have insufficient memory for storageof a user's files, especially in the case of media files (e.g., videoand image files).

SUMMARY OF CERTAIN EMBODIMENTS

Various embodiments disclosed herein can relate to a system thatincludes a case configured to receive a mobile electronic device. Thecase can include a top wall, a bottom wall, a power output interfacecoupled to the bottom wall, the power output interface configured toengage a power input interface of the mobile electronic device, whereinthe top wall is movable with respect to the power output interface froma first position in which the case is permitted to be removably attachedto the mobile electronic device to a second position in which detachmentof the case from the mobile electronic device is inhibited by engagementof the power output interface with the power input interface. The casecan include a battery, and the power output interface can be configuredto convey electrical power from the battery. The case can include anindicator component configured to indicate an amount of power in thebattery. The case can include a non-transitory computer-readable casememory configured to store data accessible by at least the mobileelectronic device via the power output interface. The system can includea non-transitory computer readable medium having stored thereon a filemanagement system configured to run on the mobile electronic device, andthe file management system can be configured to at least provide, to amedia player executing on the mobile electronic device, access to afirst media file in the case memory using a server-based communicationprotocol, and provide, to the media player, access to a second mediafile in memory of the mobile electronic device using a local storageaccess protocol.

The file management system can be configured to at least cause themobile electronic device to transmit the media file to a second mobileelectronic device via a wireless communication channel. The filemanagement system can be configured to store metadata in connection withthe first media file, and the metadata can include a tag defined by auser. The tag can include an audio recording, in some instances.

Various embodiments disclosed herein can relate to a system thatincludes a case configured to removably attach to a mobile electronicdevice. The case can include a battery, a non-transitorycomputer-readable case memory, an output interface configured to atleast engage an input interface of the mobile electronic device, conveyelectrical power from the battery to the input interface of the mobileelectronic device, and provide the mobile electronic device access todata stored in the case memory. The system can include a non-transitorycomputer readable medium having stored thereon a file management systemconfigured to run on the mobile electronic device, and the filemanagement system can be configured to at least provide, to anapplication executing on the mobile electronic device, access to data inthe case memory.

The system can be used in combination with the mobile electronic device.

The file management system can be configured to provide access to thedata in the case memory using a server-based communication protocol. Thefile management system can be configured to at least cause the mobileelectronic device to transmit the data stored in the case memory to asecond mobile electronic device via a wireless communication channel.The file management system can be configured to at least provide accessto data in memory of the mobile electronic device using a local storageaccess protocol.

The file management system can be configured to at least store metadatain connection with a file stored in the case memory. The metadata caninclude a tag defined by a user. The metadata can include a taggenerated based at least partly on calendar data stored in memory of themobile electronic device. The file management system can be configuredto provide access to a file stored in the case memory by transmitting,to a remote electronic device, a link to the file stored in the casememory.

The file management system can be configured to at least search aplurality of mobile electronic devices for a file meeting user-suppliedsearch criteria. The file management system can be configured to searchthe plurality of mobile electronic devices using at least two differentnetwork connections in response to a single search request. The filemanagement system can be configured to search the plurality of mobileelectronic devices by communicating with file management systemsexecuting on the plurality of mobile electronic devices. The filemanagement system can be configured to at least enable modification of asearch result file stored on a remote mobile electronic device of theplurality of mobile electronic devices.

The file management system can be configured to at least enablepresentation of a sequence of two or more media files, wherein at leasta first media file of the two or more media files is retrieved from afirst remote mobile electronic device, and wherein at least a secondmedia file of the two or more media files is retrieved from a secondremote mobile electronic device. The sequence of two or more media filescan include a playlist of audio files or a slide show of image files.

The file management system can be configured to search for a file basedat least in part on user activity information. The user activityinformation can include an indication of an activity that the user wasperforming when the file was created or modified.

Various embodiments disclosed herein can relate to a method ofmanufacturing a case. The method can include providing a housingconfigured to removably attach to a mobile electronic device. Thehousing can include a battery and a non-transitory computer-readablecase memory. The method can include providing an output interfaceconfigured to engage an input interface of the mobile electronic device,and the output interface can be configured to convey electrical powerfrom the battery to a input interface. The output interface can beconfigured to provide access to data stored in the case memory. Themethod can include attaching the output interface to the housing. Themethod can include providing a non-transitory computer readable mediumhaving stored thereon a file management system configured to run on themobile electronic device. The file management system can be configuredto at least provide, to an application executing on the mobileelectronic device, access to data in the case memory.

Various embodiments disclosed herein can relate to an electronic storagedevice, which can include a first wireless communication interface, asecond wireless communication interface configured to consume less powerthan the first wireless communication interface during operation, and acomputing device configured to at least (1) transmit, using the secondwireless communication interface, indicators regarding availability ofthe electronic storage device, (2) receive, using the second wirelesscommunication interface, a communication from a mobile electronicdevice, and (3) in response to the communication (i) activate the firstwireless communication interface, where the electronic storage devicetransmits data to the mobile electronic device using the first wirelesscommunication interface subsequent to activation of the first wirelesscommunication interface, and (ii) subsequent to transmitting the data tothe mobile electronic device using the first wireless communicationinterface, deactivate the first wireless communication interface.

The summary of certain embodiments provided above is not intended to belimiting and provides some example of the various embodiment disclosedherein. Various alternatives and other embodiments are disclosed herein.

BRIEF DESCRIPTION OF THE DRAWINGS

Throughout the drawings, reference numbers may be re-used to indicatecorrespondence between referenced elements. The drawings are provided toillustrate example embodiments described herein and are not intended tolimit the scope of the disclosure.

FIG. 1 shows an example embodiment of a case and a mobile electronicdevice.

FIG. 2A shows an example embodiment of a file management system for usewith the mobile electronic device.

FIG. 2B shows an example interface for tagging files according to someembodiments.

FIG. 3 shows an example embodiment of an external storage device and amobile electronic device.

FIG. 4A shows features of an example embodiment of a case for use with amobile electronic device.

FIG. 4B shows features of an example embodiment of a case for use with amobile electronic device.

FIG. 5A shows an example network environment in which a file managementsystem can search files across multiple devices.

FIG. 5B shows example data flows and interactions between multipledevices when sharing files.

FIG. 6 shows example data flows and interactions between an externalstorage device and a mobile electronic device.

FIG. 7 shows an example process for activating components of an externalstorage device to provide communication-based services to a mobileelectronic device.

FIG. 8 shows an example embodiment of mobile devices configured to sharepublic and/or private data.

FIG. 9 shows an example embodiment of charging devices configured toshare battery information with a mobile device.

FIG. 10 shows an example embodiment of sensor systems configured tocommunicate information to a mobile device.

DETAILED DESCRIPTION OF CERTAIN EMBODIMENTS

FIG. 1 shows an example embodiment of a case 100 (e.g., for use with amobile electronic device 102, such as a cell phone). Although variousembodiments are discussed herein in connection with a cell phone,various other mobile devices can be used, such as a tablet computer, alaptop computer, a wearable computing device (e.g., a smartwatch), etc.The case can include a housing 104. The outer shape of the housing 104can generally conform to the shape of the mobile electronic device 102.The housing 104 can include a recess 106, which can generally conform tothe shape of the mobile electronic device 102. The recess 106 can beconfigured to receive the mobile electronic device 102 therein. In someembodiments, the case 100 can be configured to provide protection to themobile electronic device 102 (e.g., protection from impact in the eventthat the device 102 is dropped). The case 100 and/or the mobileelectronic device 102 can include various features similar to thosedescribed in U.S. Patent Publication No. 2012/0303520 (the “'520Publication”), published on Nov. 29, 2012, filed on Jun. 8, 2012 as U.S.patent application Ser. No. 13/492,785, and titled WIRELESSCOMMUNICATION ACCESSORY FOR A MOBILE DEVICE, the entirety of which ishereby incorporated by reference and made a part of this specificationfor all that it discloses.

The case 100 can include a battery 108. The battery 108 can berechargeable. The battery 108 of the case 100 can be used to provideelectrical power to the mobile electronic device 102 (e.g., forrecharging the battery 114 of the mobile electronic device 102). Thecase 100 can include a power input interface 110, which can beconfigured to deliver electrical power to the battery 108, e.g., forcharging the battery 108. The power input interface 110 can include aport, which can be configured to receive an electrical plug (e.g., amicro USB or lightning electrical plug). In some embodiments, the powerinput interface 110 can include a wireless charging interface (e.g., forinductive charging). For example, the power input interface 110 can beconfigured to provide electrical power (e.g., to the battery 108 orother electrical components of the case 100 and/or device 102) whenplaced in an electromagnetic field (e.g., produced by a correspondingpower output interface). In some embodiments, the power input interface110 can be configured to send and/or receive data (e.g., via a wire or awireless signal).

The case 100 can include a power output interface 112, which can beconfigured to deliver electrical power to the mobile electronic device102 from the battery 108 of the case 100 (e.g., for recharging thebattery 114 of the device 102). The power output interface 112 caninclude an electrical plug (e.g., a micro USB or lightning electricalplug). In some embodiments, the power output interface 112 can include awireless charging interface (e.g., for inductive charging). For example,the power output interface 112 can be configured to produce anelectromagnetic field that can cause a power input interface 116 toprovide electrical power. In some embodiments, the power outputinterface 112 can be configured to transfer data (e.g., to or from themobile electronic device 102). The mobile electronic device 102 caninclude a power input interface 116, which can be configured to receiveelectrical power from the power output interface 112 of the case 100.The power input interface 116 can include a port that is configured toreceive the electrical plug of the case output interface 112 when themobile electronic device 102 is coupled to the case 100. In someembodiments, the power input interface 116 can include a wirelesscharging interface (e.g., for inductive charging). For example, thepower input interface 116 can be configured to provide electrical powerwhen placed in an electromagnetic field (e.g., produced by the poweroutput interface 112). In some embodiments, the power input interface116 can be configured to send and/or receive data. Electrical power canbe transferred from the battery 108 of the case 100 to the mobileelectronic device 102 for recharging the battery 114 of the mobileelectronic device 102 and/or for providing power to other components ofthe device 102 (e.g., the processor 132 and/or the display 124).

The case 100 can include a user interface 118. The user interface caninclude one or more user input elements (e.g., buttons, switches, knobs,etc.), which can be configured to receive input from the user. The case100 can be configured to transfer electrical power from the case battery108 to the mobile electronic device 102 in response to user inputreceived by the user interface 118. The user interface 118 can includeone or more user output elements (e.g., one or more lights, speakers,displays, etc.) configured to provide information to a user. Forexample, a plurality of lights can be included, which can selectivelyilluminate (e.g., in response to input from the user to the one or moreuser input elements) to indicate the amount of charge that the battery108 has. For example, half the lights can illuminate to indicate thatthe battery 108 is about half charged.

The case 100 can include a controller 120. The controller can includeone or more computing devices (e.g., computer processors). Thecontroller 120 can be implemented using one or more general purposecomputer processors, which can be configured to executecomputer-executable instructions (e.g., stored on memory 122) toimplement various features and processes discussed herein. In someembodiments, the controller 120 can include one or more specializedcomputing devices (e.g., integrated circuits) which can be configured toimplement various features and processes disclosed herein. Thecontroller 120 can be configured to control the transfer of electricalpower and/or data to and from the mobile electronic device 102. Thecontroller 120 can also control the user interface 118 and the memory122 as described herein.

The case 100 can include memory 122, which can include non-transitorycomputer-readable storage (e.g., flash memory, a hard disc, etc.). Insome embodiments, the memory 122 can store computer-executableinstructions, which can be executed by one or more computing devices(e.g., the controller 120) to implement various features and processesdiscussed herein. In some embodiments, the memory 122 can be accessibleto the mobile electronic device 102 (e.g., when the mobile electronicdevice 102 is coupled to the case 108). For example, data can betransferred from the mobile electronic device 102 to the memory 122and/or from the memory 122 to the mobile electronic device 102 via thepower output interface 112 of the case 100 and the power input interface116 of the mobile electronic device 102. In some embodiments, separateinterfaces can be used for transferring electrical power and databetween the case 100 and the mobile electronic device 102, and in someimplementations, the data and/or the electrical power can be transmittedwirelessly. In some embodiments, the memory 122 can be used assupplemental storage for files (e.g., videos, pictures, music,documents, etc.), which can be accessible to the mobile electronicdevice 102.

The mobile electronic device 102 can include a display 124, which can beconfigured to display images (e.g., text, pictures, video, etc.). Insome embodiments, the display 124 can be a touchscreen and can beconfigured to receive input from a user. In some embodiments, the mobileelectronic device 102 can include a user interface, which can includeuser input elements (e.g., one or more buttons 126, switches, knobs,microphones 128, etc.) configured to receive input from the user. Theuser interface can include user output elements (e.g., one or morelights, speakers 130, etc.) which can be configured to provideinformation to the user. In some embodiments, the display 124 can beconfigured to provide information to the user and/or to receive inputfrom the user, and the display 124 can be considered part of the userinterface 126. The one or more microphones 128 can be configured toreceive voice commands from a user and/or to receive sounds for a phonecall. The one or more speakers 130 can be configured to providenotifications and other information to the user and/or to output soundfor a phone call.

The mobile electronic device 102 can include a controller 132, which caninclude one or more computing devices (e.g., computer processors). Thecontroller 132 can be implemented using one or more general purposecomputer processors, which can be configured to executecomputer-executable instructions (e.g., stored on memory 134 or 122) toimplement various features and processes discussed herein. In someembodiments, the controller 132 can include one or more specializedcomputing devices (e.g., integrated circuits) which can be configured toimplement various features and processes disclosed herein. Mobileelectronic device 102 can include memory 134, which can includenon-transitory computer-readable storage (e.g., flash memory, a harddisc, etc.). In some embodiments, the memory 134 can storecomputer-executable instructions, which can be executed by one or morecomputing devices (e.g., the controller 132) to implement variousfeatures and processes discussed herein. The mobile electronic device102 can also include at least one wireless communication interface 136.The wireless communication interface 136 can include one or moreantennas and can be configured to receive and/or transmit data (e.g.,via WiFi, Bluetooth, Near Field Communication (NFC), Code DivisionMultiple Access (CDMA), Global Systems for Mobile Communications (GSM),etc.).

The case battery 108 can be used to recharge the battery 114 of themobile electronic device 102 and/or to provide electrical power directlyto the display 124, controller 132, memory 134, user interface, etc. Thecase battery 108 can provide electrical power to components of the case100 (e.g., the processor 120, memory 122, and/or user interface 118).The battery 114 of the mobile electronic device 102 can be used to powercomponents on the case 100 (e.g., the processor 120, memory 122, and/oruser interface 118), for example, if the battery 108 is depleted. Insome cases, using the battery 108 of the case 100 to power thecomponents of the case 100 can be advantageous by avoiding or reducingthe draining of the battery 114 of the device 102 by operating the case100 (e.g., accessing the memory 122).

In some embodiments, the housing 104 may include multiple (e.g., two ormore) portions that can be separated from each other. For example, thehousing 104 may include at least a first portion 101 and a secondportion 103. The first and second portions 101, 103 may form the housing104 by connecting or coupling to each other (e.g., via one or more tabson one portion and one or more corresponding recesses on the otherportion, by a tongue on one portion and a corresponding groove on theother portion, or by other attachment mechanisms, etc.). A user mayinstall the case 100 onto the mobile electronic device 102 (or installthe mobile electronic device 102 into the case 100) by separating thefirst and second portions 101, 103. For example, the first portion 101may be moved away from the second portion 103 such that a distancebetween a top wall 105 of the recess 106 and a bottom wall 107 of therecess 106 is increased (or a distance between the top wall 105 and thepower output interface 112 is increased). Thus, additional space may becreated to allow the mobile electronic device 102 to be placed into therecess 106. The first portion 101 may then be advanced toward the secondportion 103, reducing the distance between the top wall 105 and bottomwall 107, thereby exerting a gripping force one the mobile electronicdevice 102, causing the power output interface 112 to be inserted intothe power input interface 116 of the mobile electronic device 102, orotherwise securing the mobile electronic device 102 within the recess106.

In some embodiments, the housing 104 may include multiple portions thatstack onto each other to “sandwich” or otherwise secure the mobileelectronic device 102 into the case 100. For example, the housing 104may include a back portion that corresponds to the back (e.g., the rearface) of the mobile electronic device 102 and a front portion thatcorresponds to the front (e.g., the front face or display face) of themobile electronic device 102. The mobile electronic device 102 may beplaced into a recess in a first portion (e.g., the back portion or thefront portion), and the complimentary portion (front portion or backportion, respectively) may be coupled to the first portion to secure themobile electronic device 102.

In some embodiments, the housing 104 (or some portion thereof) may be atleast partially flexible such that the mobile electronic device 102 canbe inserted into, and removed from, the recess 106, even if the recess106 is substantially the same size (e.g., width, length, and/orthickness) as the mobile electronic device 102. Alternatively, or inaddition, the power output interface 112 of the case 100 may bepivotable or otherwise movable to allow insertion into the power inputinterface 116 of the mobile electronic device 102. The mobile electronicdevice can then be placed into the recess 106 of the case 100 as thepower output interface 112 pivots or otherwise moves back into itsoriginal position or orientation with respect to the housing 104.

In some embodiments, the case 100 can communicate with an externalcomputing device (not shown), such as a personal computer. For example,a cable can extend between the power input interface 110 and theexternal computing device, and data can be transferred using the cable.In some implementations, the case 100 can include a wirelesscommunication interface, and data can be transferred wirelessly. In someembodiments, the case 110 can be configured transmit data from themobile electronic device 102 to the external computing device and/or totransmit data from the external computing device to the mobileelectronic device 102. For example, by coupling the external computingdevice to the case 100 via a cable, the external computing device cancommunicate with the mobile electronic device 102 (e.g., memory 134)and/or the case 100 (e.g., memory 122). In some embodiments, theexternal computing device can access the memory 134 of the mobileelectronic device 102 via the same interface and/or protocols as if theexternal computing device were communicating directly with the mobileelectronic device 102 (e.g., via a cable coupled to the power inputinterface 116), without the case 100. In some embodiments, the memory122 of the case 100 can be accessible to the external computing deviceas an extension of the mobile electronic device 102 (e.g., using thesame interface and/or protocols used to access the memory 134 of themobile electronic device 102). In some embodiments, the memory 122 ofthe case 100 can be accessible separate from the memory 134 of themobile electronic device 102 (e.g., as a separate drive). In someembodiments, the memory 122 of the case 100 can be accessible to anexternal computing device, even when no mobile electronic device 102 iscoupled to the case 100. In some embodiments, a user can store files onthe memory 122 of the case 100 and can access the files on the memory122 via an external computing device. Accordingly, the memory 122 on thecase 100 can be used for storage and transfer of files instead of a USBflash drive, optical disc, or other computer storage device. Because thememory 122 is incorporated into the case 100 that is coupled to themobile electronic device 102, the memory 122 can be less likely to belost, as compared to a small computer storage device such as a USB flashdrive or optical disc.

Various embodiments disclosed herein can relate to one or more softwareprograms (e.g., one or more apps) which can run on the mobile electronicdevice 102 (e.g., using the controller 132), as discussed herein.Various features described herein can be implemented in single softwareprogram or in multiple software programs. Various embodiments can relateto one or more computer-readable storage devices (e.g., one or morenon-transitory storage media) having executable instructions storedthere, and the executable instructions can be configured to run on oneor more computer processors to implement various features and processesdescribed herein. In some embodiments, one or more specialized computingdevices (e.g., integrated circuits) can be configured to implementvarious features and processes disclosed herein.

With reference to FIG. 2A, some embodiments can relate to a filemanagement system 138. The file management system 138 can be implementedby the controller 132 (e.g., executing machine-executable instructionsstored on the case memory 122 and/or on the device memory 134). Forexample, the file management system 138 may include one or moreexecutable modules that can be loaded into memory 122 or 134 andexecuted by the controller 132. The file management system 138 may beintegrated into an operating system of the case 100 and/or device 102,or the file management system 138 may be an add-in component, astand-alone application or service, some combination thereof, etc.

The file management system 138 can be configured to access files 140 onthe device memory 134 and files 142 on the case memory 122. The filemanagement system 138 can include a file database 144, which can bestored on one or more computer-readable storage devices (e.g., the casememory 122 and/or the device memory 134). The file database 144 caninclude metadata associated with the files 140 on the device memory 134and/or the files 142 on the case memory 122. The metadata can includeone or more of the file location, the file type, the file creation time,one or more file edit times, the file version, the location where thefile was created, user activity information associated with the file,security information regarding who may access the file and/or what theuser may do (e.g., roles, permissions), etc.

The file management system 138 can be configured to provide a userinterface 146, which can be a graphical user interface (GUI), (e.g., onthe display 124 of the mobile electronic device 102), and the userinterface 146 can be configured to enable a user to sort and/or searchthe files 140 and 142 regardless of whether they are stored on thedevice memory 134 or on the case memory 122 (or on some other device, asdescribed in greater detail below). For example, the user interface 146or some other component can be configured to receive input from the user(e.g., via a touchscreen 124, via user input elements 126, via a voicecommand received by a microphone, etc.). In some embodiments, user inputcan be received by another device and the user input data can betransmitted to the mobile electronic device 102. For example, a wearablecomputing device (e.g., a smartwatch, etc.) can be configured to receiveinput from a user (e.g., via a touch screen, via a voice commandreceived by a microphone, etc.). The wearable computing device cantransmit user input data to the file management system 138 (e.g., viathe wireless communication interface 136). The file management system138 can be configured to sort and/or search the files 140 and 142 inresponse to the user input. For example, the user interface 146 can beconfigured to enable the user to select a file type, and the userinterface can display all files of that type that are stored on eitherthe device memory 134 or the case memory 122, and regardless of the filelocation (e.g., regardless of what folder the file is in). For example,the user can provide user input selecting image files, and the filemanagement system 138 can access the file database 144 to identify allimage files stored in the case memory 122 and/or stored in the devicememory 134, and the identified files can be presented (e.g., as icons,or on a list) on the user interface 146. The user interface 146 canenable the user to sort the files by various parameters, such as filetype, file creation time, file edit time, location informationassociated with the file, user activity information associated with thefile, etc. The user interface 146 can enable the user to search forfiles on the case memory 122 and/or on the device memory 134, asdiscussed herein.

In some embodiments, the file management system 138 can be configured toperform operations (open, view, edit, delete, share, etc.) on the files140 and/or 142. For example, the user interface 146 can enable the userto provide user input for selecting a file. For example, the userinterface 146 can display icons associated with the files 140 and/or 142and the user can select an icon associated with a file. The userinterface 146 can be configured to enable the user to select anoperation for the file (e.g., to open, view, edit, delete, or share thefile). In some embodiments, the file management system 138 can beconfigured to open a selected file using a different program. In someembodiments, the file management system 138 can be configured to performoperations (e.g., open, view, edit, delete, or share) on the files 140and/or 142 directly from the file management system 138 or from arelated program that is configured to function with the file managementsystem 138 (e.g., by providing updated metadata regarding the files 140and/or 142 back to the file management system 138). For example, thefile management system 138 can include a media player which can beconfigured to use (e.g., view or play) media files (e.g., images,videos, or music files). In some embodiments, the file management system138 can access a media player 148 of the mobile electronic device 102(e.g., stored in the device memory 134) to use (e.g., view or play)media files.

In some instances, the mobile electronic device 102 may not be designedto use external memory (e.g., the case memory 122). The file managementsystem 138 can enable the mobile electronic device 102 to use filesstored on the case memory 122 as well as on the device memory 134. Forexample, in some instances, the media player 148 of the mobileelectronic device 102 is not configured to use a media file 150 that isstored on an external local memory (e.g., on the case memory 122). Insome instances the media player 122 of the device 102 can be configuredto use (e.g., view or play) media files that are stored on the devicememory 134 and/or that are stored remotely on a server (e.g., via theinternet). For example, the media player 148 can include a local memoryprotocol (e.g., a first set of instructions) for accessing a media fileon the local device memory 134, and the media player 148 can include aserver protocol (e.g., a second set of instructions) for accessing amedia file (e.g., streaming a video) from a server (e.g., over theinternet). In some embodiments, in order to enable use of a media file150 stored on the case memory 122, the document management system 138can include a local server 152 (e.g., a hypertext transfer protocol(HTTP) server) that is configured to access the media file 150 on thecase memory and present the media file 150 to the media player 148 as afile being read from a server (e.g., using the server protocol). Forexample, the local server 152 can stream a media file 150 (e.g., a videoor music file) from the case memory 122 to the media player 148.

In some embodiments, files can be created using the file managementsystem 138. For example, the user interface 146 of the file managementsystem 138 can be configured to receive user input associated withcreating a new file. For example, the file management system 138 canaccess a camera 152 of the mobile electronic device 102 to create animage file or video file in response to input received from the user. Insome embodiment, the file management system 138 can access the cameraprogram of the mobile electronic device 102 (e.g., stored on the devicememory 134) in to create an image file using the camera. For example,the file management system 138 can call the camera applicationprogramming interface (API) in response to user input for taking apicture or video.

The file management system 138 can be configured to store metadata forthe files 140 and 142 (e.g., in response to the creation of the file).For example, the file management system 138 can generate and/or storemetadata for files created using the file management system 138. In someembodiments, the file management system 138 can be running in thebackground (e.g., as a service of the operating system of the device onwhich the file management system 138 is running). The file managementsystem 138 can be notified by the operating system or otherwiseconfigured to recognize when a file is created or modified by anotherprogram, and the file management system 138 can generate and/or storemetadata (e.g., in response to a file being created or modified by aprogram other than the file management system 138). The metadata can bestored as part of the files 140 and/or 142 themselves, or the metadatacan be stored in metadata files (e.g., in the file database 144) thatare associated with the files 140 and/or 142. The metadata can includeone or more of the file location, the file type, the file creation time,one or more file edit times, the file version, the geographical locationwhere the file was created, user activity information associated withthe file, etc.

The metadata can include geographical location information. For example,the file management system 138 can be configured to communicate with alocation sensor 154 (e.g., of the mobile electronic device 102) that isconfigured to provide geographical location information. For theexample, the location sensor 154 can be a global positioning system(GPS) element. When a file 140 or 142 is created or modified, the filemanagement system 138 can obtain geographic location information fromthe location sensor 154 and can store that geographic locationinformation as metadata for the file 140 or 142 (e.g., stored in thefile database 144).

The metadata can include user activity information. For example, thefile management system can be configured to communicate with one or moreactivity sensors 156. The activity sensors 156 can be configured toprovide user activity information (e.g., sleeping, running, driving,etc.). In some embodiments, multiple activity sensors 156 can providedata which can be analyzed to determine user activity information. Anactivity analysis element 158 can be included (e.g., as part of the filemanagement system 138 or as a separate program, which can be configuredto communicate with the file management system 138). The activityanalysis element 158 can be configured to receive data from the one ormore activity sensors 156 and determine user activity information basedat least in part on the data received from the one or more activitysensors 156. For example, the activity sensors 156 can be included onthe mobile electronic device 102 or on a wearable computing device(e.g., a smartwatch, smartband, necklace, ear piece, eyewear, etc.). Insome embodiments, multiple activity sensors 156 on multiple devices canprovide data to the activity analysis element 158. When a file 140 or142 is created or modified, the file management system 138 can obtainuser activity information from the activity analysis element 158 and/orthe one or more activity sensors 156, and can store the user activityinformation as metadata for the file 140 or 142 (e.g., store in the filedatabase 144). Various features relating to activity determination,which can be used in the systems and methods disclosed herein, aredescribed in U.S. Provisional Patent Application No. 62/057,931, filedSep. 30, 2014, and titled SYSTEM AND METHOD FOR ACTIVITY DETERMINATION,which is hereby incorporated by reference in its entirety and made apart of this specification for all that it discloses.

The metadata may also or alternatively include descriptive tags, or tagsindicative of the context of the file. In some embodiments, the tags maybe automatically applied to a file or suggested for a file, defined byor selected by a user, etc. For example, a mobile electronic device 102may include a camera. A user of the mobile electronic device 102 can usea camera application to capture images and/or videos of particularsubjects, such as people, places, events, and the like. Illustratively,the user may capture multiple (e.g., 2, 10, or more) images of aparticular subject, such as a graduation party. Later the same day, theuser may capture multiple images of a different subject, such as asporting event. By tagging the images for each event accordingly (e.g.,adding a tag to the photos from the graduation party indicating thegraduation party at which the photos were taken; adding a tag to thesporting event photos indicating the sporting event at which the photoswere taken), the user can later search for and retrieve photos for thespecific event without necessarily knowing which date the event tookplace, that multiple events took place on the same day, etc. By way ofexample, the tags can be used to indicate a one-time event (e.g., agraduation party), to indicate an event that occurs over the source ofmultiple days (e.g., a vacation), to indicate a series of related eventsthat occur on different days (e.g., Sally's soccer games), or toindicate a category of events (e.g., work-related events orfamily-related events). Conventional file management systems, and evenimage-specific file management systems, may organize images in variousways that make it difficult to locate files of only one of the twosubjects. For example, conventional image management systems mayorganize files by date, and may therefore group the two different eventstogether. As another example, a conventional image management system mayorganize files by geographic location, and may therefore group thegraduation party images with other images taken at the same location atanother time (e.g., not in connection with the graduation party).

FIG. 2B shows a mobile electronic device 102 displaying, on a visualdisplay 124, an example user interface for adding tags to photos. A usermay use a camera application (or some other application or service forcapturing photos) on the mobile electronic device 102. The applicationmay provide an option 200 for adding tags to past or future photographs,managing tags, etc. Returning to the example above, a user may be takingphotographs for a graduation party. The user may add a tag to each ofthe photos that are taken at the party so that the user (or other users)may later conduct a search using the tag. Use of the tag in this way canhelp users more quickly find the photos taken at the party.

As shown, a user may have multiple options 202, 204, and 206 for addingtags. The options may be predefined by the camera application (e.g., thecamera application may be programmed with a set of possible tags, suchas “graduation,” “anniversary,” “birthday,” “holiday,” “vacation,”“work,” “family,” and the like). In some embodiments, users may bepermitted to define their own tags instead of, or in addition to, usingtags predefined by the camera application. For example, options 202 and204 may be tag options provided by the camera application or previouslyadded by the user, and option 206 may be an option to add a new tag. Auser can select option 206 and enter the new tag in the text box 208. Insome embodiments, the system can be configured to allow a user to inputa new tag name by a voice command (e.g., by speaking the words“graduation party” into a microphone on the mobile electronic device102).

In some embodiments, the camera application may automatically generateor recommend tags to the user. For example, the camera application mayhave access to the user's calendar (e.g., the mobile device 102 may havea calendar application), and can determine that there is a birthdayparty scheduled for the current date and time. In the example shown inFIG. 2B, the camera application may determine that the user is scheduledto attend both a graduation party and a sporting event. Option 202 maycorrespond to the graduation party, option 204 may correspond to thesporting event, and option 206 may correspond to a user-definable tag.The user may select option 202, and all photos taken with option 202selected may be tagged with the graduation party tag.

Tagging a file can include adding metadata to the file, storing tag datain a separate database of file properties, storing the file in a certainlocation (e.g., a tag-specific drive or directory), etc. The tag datamay be automatically generated by the camera application, the filemanagement system 138, or some other module or component. The tag itselfmay be or include the name of the tag (e.g., for a file tagged with the“graduation party,” the tag that is added to the file metadata, storedin the database, etc. may be the words “graduation party”). In someembodiments, the tag may be an identifier of the tag, such as an integerthat is uniquely associated with the particular tag. In someembodiments, the tag may be an encoded version of the tag name, or dataderived therefrom. For example, the tag may be a hash of the tag name.

In some embodiments, tags may not be text-based, but may instead beaudio and/or visual-based tags. For example, a user may tag photographs,documents, and the like with a voice memo, such as a brief spokendescription of the associated files. The voice memo may be stored as afile or stream of audio data. The audio data may be embedded into thefile or stored separately from the file and associated with the file insome way. For example, a user may speak into (or in the presence of) themicrophone 128. Audio data generated by the microphone (or audio datagenerated using a signal generated by the microphone) may be stored in adata store on the mobile electronic device 102 or otherwise under thecontrol of the file management system 138. As another example, the audiodata may be stored at a network storage provider (e.g., a “cloud-based”storage provider) and referenced by metadata embedded into or associatedwith the file (e.g., a link to a location from where the audio data maybe streamed). As yet another example, a spoken utterance made by a userfor purposes of adding a memo-based tag may be processed using anautomatic speech recognition (ASR) component or service to generate atextual representation of the utterance, such as a transcription of theutterance. The transcription may be embedded into tagged files, storedin association with tagged files, etc. In some embodiments, the textualrepresentation of the utterance can be used for the name of the tag(e.g., “graduation party”).

Although the example described above with respect to FIG. 2B relates totagging of photos, the example is illustrative only. Other types offiles may also tagged and searched, such as music files, video files,slide shows, word processing documents, spreadsheets, text messages,emails, and the like.

The tags that are applied to or otherwise associated with files may beused to search, sort, organize, and otherwise manage files. In someembodiments, the file management system 138 may include a file searchingelement 192, described in greater detail below. The file search element192 may allow a user to select or submit a tag to use in a file search,and the file search element 192 can locate files with (or associatedwith) tags that match or satisfy searches in some way. In someembodiments, the system can be used to assign more than one tag to asingle image or other type of file (e.g., a photo can be assigned thetags “family” and “graduation party”), which can enable the user toperform searches at various levels of specificity. As also described ingreater detail below, the file search element 192 or some other moduleor component of the file management system 138 can use tags to searchfor files across multiple devices, potentially belonging to or otherwiseoperated by different users. As long as the users used the same tag totag files, the files may be found by searching for the tag regardless ofthe device on which they are stored.

In some embodiments, the file management system 138 can include a filesharing element 160. The file sharing element 160 can be configured toshare files 140 and/or 142 with an external computing device 162 (e.g.,a cell phone, a tablet computer, a laptop computer, a desktop computer,or a wearable computing device). In some embodiments, the externalcomputing device 162 can include features similar to those discussed inconnection with the mobile electronic device 102. The file sharingelement 160 can be configured to communicate with the external device162 wirelessly, such as via the wireless communication interface 136(e.g., using one or more of WiFi, Bluetooth, Near Field Communication(NFC), etc.). In some embodiments, the file sharing element 160 can beconfigured to provide a link to a file 140 or 142 to the external device162 (e.g., via the wireless communication interface 136). The filesharing element 160 can create a link (e.g., a hypertext transferprotocol (HTTP) link) to the file 140 or 142 to be shared. The link canbe transmitted to the external computing device 162 in various manners,such as by a text message, an email, a NFC communication, etc. In someembodiments, the link may include encoded access information, such as anaccount or device identifier, a security token, or some otherinformation that may be used to determine whether the requestor ispermitted to access the linked file. For example, the link may includeauthentication and/or authorization information that the file sharingelement 160 or some other module or component of the file managementsystem 138 can use to enforce security policies with respect to sharingof the linked file. In some embodiments, the external computing device162 can have a file management system 164 similar to the file managementsystem 138 of the mobile electronic device 102. In some implementations,the file sharing element 160 can be configured to communicate the linkvia a communication channel between the file management system 138 onthe mobile electronic device 102 and the file management system 164 ofthe external computing device 162.

The external device 162 can use the transmitted link to access the file140 or 142 that is stored on the case memory 122 or on the device memory134. In some embodiments, the file sharing element 160 can function as aserver. For example, the file sharing element 160 can be configured toprovide links to files 140 and/or 142 to an external device 162. Arequest from the external device 162 associated with a shared link canbe received by the file sharing element 160. In response to the requestreceived form the external device 162, the file sharing element 160 canextract any access information provided with the request (e.g.,information appended onto the link or embedded within the link andprovided to the file sharing element 160 in connection with therequest). The file sharing element 160 can then verify that theuser/device that is requesting access to the file is permitted to accessthe file, and provide the external device 162 with access to the fileassociated with the link. In some embodiments, the file sharing element160 can transmit a copy of the requested file 140 or 142 to the externalcomputing device 162. In some embodiments, the file sharing element 162can transmit one or more portions of the requested file 140 or 142 tothe external device 162. For example, in some embodiments, the filesharing element 160 can be configured to stream a video file, a musicfile, or other file type, to the external device 162. In someembodiments, the file sharing element 160 can share a single file 140 or142 with multiple external devices (e.g., multi-user streaming). In someembodiments, the file sharing element 160 can provide the externaldevice 162 with read-only access to the file. In some embodiments, thefile sharing element 160 can receive information from the externaldevice 162 and can modify the shared file 140 or 142 based at least inpart on the information received form the external device 162. Forexample, the external device 162 can send a modified version of the file140 or 142 to the file sharing element 160 and the file managementsystem 138 can replace the file 140 or 142 with the received modifiedversion thereof, or can modify the file 140 or 142 based at least inpart on the modified version thereof.

In some embodiments, the file sharing element 160 can be configured toprovide access to the file 140 or 142 without sending a copy of the file140 or 142 to the external device 162. For example, in some embodiments,the file sharing element 160 can provide image information to theexternal device 162, and the image information can correspond to thefile 140 or 142. In some implementations, the image information can bebased at least in part on the image that would be displayed on thedisplay 124 if the file were accessed by the mobile electronic device102. By way of example, if the shared file 140 or 142 is a text file,the file sharing element 160 can generate an image file of the imagethat would be displayed on the display 124 if the text file 140 or 142were opened on the mobile electronic device 102. The image file (or amodified version thereof) can be transmitted to the external computingdevice 162 for display. Thus, the image displayed on the externalcomputing device 162 can show the formatting of the text, withouttransmitting the text file itself to the external computing device 162.Other file types (including video files, image files, audio files, etc.)can be similarly hosted by the mobile electronic device 102 to providethe external computing device 162 with access to the files. In someembodiments, audio information that corresponds to the shared file canbe transmitted to the external computing device 162 from the filesharing element 160 (e.g., in addition to or instead of the imageinformation discussed above).

By hosting the file on the mobile electronic device 102, the externaldevice 162 can access files 140 and/or 142 on the mobile electronicdevice 102 which are not themselves compatible with the externalcomputing device 162. Thus, the file sharing element 160 can enable filesharing across different platforms (e.g., between the iOS operatingsystem used by Apple, the Android operating system, the Windowsoperating system, etc.). For example, in some embodiments, the mobileelectronic device 102 can operate on a first platform (e.g., iOS) andthe external computing device 162 can operate on a second platform(e.g., Android). A file 140 or 142 can be compatible with the firstplatform, but not compatible with the second platform. Thus, merelytransferring a copy of the file 140 or 142 to the external device 162may not enable the user of the external device 162 to access the file140 or 142. The file sharing element 160 can host the file 140 or 142 onthe mobile electronic device 102 and can send data (e.g., image and/oraudio information) that corresponds to the file 140 or 142 to theexternal device 162. Thus, the user of the external device 162 can beprovided with access to the file 140 or 142 without opening the file onthe external device 162.

In some embodiments, the hosted file data (e.g., image informationand/or audio information) sent by the file sharing element 160 to theexternal device 162 can be tailored to the external device 162. Forexample, the file sharing element 160 can output the data in a formatthat is compatible with the external computing device 162. Thus, thefile sharing element 160 can provide different data depending on thetype of the external device 162 (e.g., an iOS platform, an Androidplatform). In some embodiments, the resolution of the image informationtransferred by the file sharing element 160 can be based at least inpart on the type of the external device 162 (e.g., based on theresolution of the display of the external device 162). In someembodiments, the external device 162 can send information relating tothe type of the external device 162 to the file sharing element 160. Forexample, when the external device 162 requests a file 140 or 142 (e.g.,via a link sent from the file sharing element 160), the request caninclude information relating to the type of the external device 162. Insome embodiments, the external device 162 (e.g., the file managementsystem 164 thereof) can modify the hosted file data received from thefile sharing element 160 (e.g., to change the format or resolutionthereof).

In some embodiments, the file sharing element 160 may communicate (orcause communications) with the external device 166 using a display-basedcommunication protocol that specifies mechanisms for transmitting bitmappresentations of visual display updates and encoded graphical userinterface input via a network. Illustratively, the file sharing element160 may provide a view of a file using Remote Desktop Protocol (RDP),X-Windows protocol, Virtual Network Computing (VNC) protocol, RemoteFrame Buffer (RFB) protocol, or the like. In one illustrative example,the file sharing element 160 can receive user input information from theexternal device 162, and can adjust the hosted file data (e.g., imageand/or sound information) that is sent to the external device 162 basedon the user input information. Examples of user input include scrollingdown in a text document, zooming in or out of the image file, pausing avideo file, muting the audio in a video file, changing the treble orbase audio elements in a music file, etc. The external device 162 canreceive user input (e.g., via a touchscreen, voice command, etc.). Theuser input data can be sent to the file sharing element 160 (e.g., viathe wireless communication interface 136). The file sharing element 160can interpret the received user input data and can take action based onthe received user input data. For example, the user input data caninclude a location of a touch on a touchscreen of the external device162, and the file sharing element 160 can map the location of the userinput data to a corresponding location on the touchscreen display 124and can take action that is associated with a touch at the correspondinglocation of the touchscreen 124. By way of example, a user of theexternal device 162 can touch the portion of the display on the externaldevice 162 that is displaying the portion of the image datacorresponding to a virtual button, and the mobile electronic device 102can respond by taking the action associated with the virtual button. Insimilar manner, the user of the external device 162 can provide inputthat causes the mobile electronic device 102 to take various actions. Insome cases, the external device 162 can have read-only access to thefiles 140 and/or 142. In some implementations, input received by theexternal device 162 can be used to edit files 140 and/or 142 on themobile electronic device 102, and in some cases to save modifiedversions of the files 140 and/or 142.

In some embodiments, the file sharing element 160 can be configured totranslate files 140 and/or 142 to a different format (e.g., to becompatible with the external device 162 with which the files 140 and/or142 are being shared). For example, a request from the external device162 for a file can include an indication of the type of the externaldevice 162 (e.g., iOS platform or Android platform). If the requestedfile 140 or 142 is not in a format that is compatible with the externaldevice 162, the files sharing element 160 can modify the requested file140 or 142 or produce a new modified version of the file 140 or 142 thatis compatible with the external device 162, which is then shared withthe external device 162. By way of example, the mobile electronic device102 can have a first platform (e.g., iOS) and can have contact files(e.g., with information relating to one or more of the contacts' names,phone numbers, email addresses, home addresses, etc.) that are in aformat compatible with the first platform. The external device 162 canhave a second platform (e.g., Android) that uses contact information ofa different format that is compatible with the second platform. To sharea contact file from the mobile electronic device 102 (e.g., which usesthe first platform) to the external device 162 (e.g., which uses thesecond platform), the file sharing element 160 can produce a new ormodified file that is compatible with the second platform. The filesharing element 160 can extract the contact data out of the originalfile in the original format, and can produce a new or modified contactfile from the extracted data that is in a format compatible with theexternal device 162. The new or modified contact file can be shared with(e.g., transmitted to) the external device 162, which can read the newor modified file, which is in the format that is compatible with theexternal device 162. Various data conversion techniques can be used tochange data from various file formats to another different file formats.The file sharing element 160 can be configured to convert the format ofvarious types of file, including text message files, contact files,image files, video files, document files, etc.

In some embodiments, the receiving device can perform the formatconversion (e.g., similar to the format conversion discussed above).Thus, in some cases, a file 140 or 142 can be shared with the externaldevice 162, and the external device 162 can produce a new file or amodified version of the file that is in a different format that iscompatible with the external computing device 162.

In some embodiments, the file database 144 can store data in aplatform-generic format, or in a format from which platform-specificfiles can be extracted, generated, etc. For example, the file sharingelement 160 can be configured to extract data from a file of aplatform-specific format and to save the extracted data inplatform-generic format (e.g., in the file database 144). In someembodiments, the file sharing element 160 can be configured to extractthe data and provide it in a platform-generic format. When data is to beshared from the mobile electronic device 102 to the external computingdevice 162, the platform-generic data can be converted to a format thatis compatible with the external device 162, or the platform-generic datacan be shared with the external device 162, which can convert the datato a file format that is compatible with the external device 162. Insome embodiments, the file management system 164 of the external device162 can be configured to receive and utilize the platform-generic datawithout converting it to a different format.

In some embodiments, the file management system 164 of the externaldevice 162 can include a file sharing element, which can be similar tothe file sharing element 160, and files from the external device 162 canbe shared with the mobile electronic device 102 (e.g., similar to thetechniques discussed above).

In some embodiments, the file sharing element 160 can be configured toshare a plurality of files 140 and/or 142 with the external device 162,and the external device 162 can be used to manage the files 140 and/or142 that are stored on the case memory 122 and/or on the device memory134 using the external device 162. In some embodiments, the externaldevice 162 can be a laptop computer or a desktop computer, which in somecases can be better equipped to enable a user to manage a large numberof files 140 and/or 142.

Many variations are possible. For example, the file management system138 can communicate with the external device 162 via a wired connection(e.g., a cable engaged with the power input interface 110) instead ofthe communication interface 136. Various elements described inconnection with the file management system 138 can be separated into oneor more additional components, and in some cases can be implemented in aseparate device. For example, the activity analysis element 158 can beincorporated into a wearable computing device and can be configured totransmit user activity data to the mobile electronic device 102.

In some embodiments, the mobile electronic device 102 can be configuredto communicate with an external storage device 166. In some embodiments,the external storage device can include a file management system 168,which can include features similar to those discussed in connection withthe files management system 138 of the mobile electronic device 102.

FIG. 3 shows an example embodiment of an external storage device 166,which can be used with the mobile electronic device 102. Although thecase 100 is not shown in FIG. 3, the external storage device 166 can beused with the mobile electronic device 102 with or without the case 100attached thereto. The external storage device 166 can include a housing170, which can support or enclose various other components of the device166. The external storage device 166 can include a battery 172. Thebattery 172 can be rechargeable. A power input interface 174 can beconfigured to provide electrical power to the battery 172 (e.g., forrecharging the battery 172). The power input interface 174 can besimilar to the power input interface 110 discussed in connection withthe case 100. The power input interface 174 can include a portconfigured to receive an electrical plug, or can be configure to receiveelectrical power wirelessly (e.g., via inductive charging). The powerinput interface 174 can also send or receive data (e.g., via a cablecoupled to the port).

The battery 172 can be configured to provide electrical power to a poweroutput interface 176. The power output interface 176 can be similar tothe power output interface 112 discussed in connection with the case100. The power output interface 176 can include a port configured toreceive an electrical plug 178, or can be configured to perform wirelesscharging (e.g., via inductive charging). In some embodiments, the poweroutput interface 176 can include an electrical plug (e.g., that isconfigured to engage the power input interface 110 or 116. The poweroutput interface 176 can be configured to send or receive data (e.g.,via a cable coupled to the port). In some embodiments, an electricalcable 180 can be used to transfer electrical power and/or data betweenthe external storage device 166 and the mobile electronic device 102and/or case 100. In some implementations, electrical plugs 178 and 182can be positioned at the ends of the cable 180. In some embodiments, asingle port on the external storage device 166 can receive electricalpower and can output electrical power.

The battery 172 can be electrically coupled to various components of theexternal storage device 166, and the battery 72 can provide electricalpower to operate the various components. In some embodiments, thebattery 172 can output electrical power (e.g., via the power outputinterface 176) to another device (e.g., to the mobile electronic device102 and/or the case 100). Thus, the external storage device 166 can beused to recharge the battery 114 of the mobile electronic device 102, orthe battery 108 of the case, or batteries on various other devices.

The external storage device 166 can include a controller 184. Thecontroller 184 can include one or more computing devices (e.g., computerprocessors). The controller 184 can be implemented using one or moregeneral purpose computer processors, which can be configured to executecomputer-executable instructions (e.g., stored on memory 186) toimplement various features and processes discussed herein (e.g., toimplement features of the file management system 168). In someembodiments, the controller 184 can include one or more specializedcomputing devices (e.g., integrated circuits) which can be configured toimplement various features and processes disclosed herein.

The external storage device 166 can include memory 186, which caninclude non-transitory computer-readable storage (e.g., flash memory, ahard disc, etc.). In some embodiments, the memory 186 can storecomputer-executable instructions, which can be executed by one or morecomputing devices (e.g., the controller 184) to implement variousfeatures and processes discussed herein. The memory 186 can also be usedto store files (which can be made accessible to the mobile electronicdevice 102 and/or to one or more other devices).

The external storage device 166 can include a wireless communicationinterface 188, which can be configured to communicate wirelessly withother devices (e.g., via WiFi, Bluetooth, NFC, etc.). The wirelesscommunication interface 188 can be used to transfer files, links tofiles, metadata, other data relating the files that are stored on thememory 186 (e.g., to the mobile electronic device 102 and/or to otherelectronic devices). In some embodiments data can be transferred via awire connection (e.g., via the cable 180). In some embodiments, theexternal storage device 166 can be used as a central storage locationfor multiple users. In some embodiments, files can be transmitted inparts (e.g., streaming a video) such that access to the file can beginwith little to no delay. In some embodiments, the external storagedevice 166 can use multiple communication protocols. For example, theexternal storage device 166 can use Bluetooth to communicate withdevices within a first range, and WiFi to communicate with deviceswithin a second range that is larger than the first range. In someembodiments, the external storage device 166 can include or can be incommunication with a router device (e.g., a 4G router) to enable theexternal storage device 166 to communicate with remote devices.

In some embodiments, the wireless communication interface 188 mayprovide multiple (e.g., two or more) distinct communication modes, suchas a first or “normal power” mode and a second or “low power” mode. Oneexample of a multi-mode wireless communication interface is a deviceimplementing the Bluetooth 4.0 (or later) standard. Such a device canprovide a “classic” Bluetooth communication mode and also a BluetoothLow Energy (“BLE”) mode. As used herein, the terms “low power” and“normal power” are relative terms, and the range of modes and/or devicesdescribed using the terms may overlap to some degree. In addition, many“normal power” modes or devices may consume or require much less powerthan certain other modes or devices. Generally described, the “lowpower” devices and modes of the present disclosure consume or requireless power than the “normal power” devices and modes of the presentdisclosure.

A multi-mode wireless communication interface 188 may use a normal-powermode to transfer data, such as files managed by the file manager system168 described herein. The wireless communication interface 188 may use alow-power mode to advertise the availability of the external storagedevice 166 for connection and use. The wireless communication interface188 may use a lower-power mode to receive a communication (e.g., arequest for data) from another device (e.g., mobile electronic device102). Illustratively, the external storage device 166 (or certaincomponents thereof, such as the controller 184) may enter a “sleep” modeor some other low- or no-power mode when not in use, such as when theexternal storage device 166 is not providing power, data, or otherresources or functionality to any mobile electronic device 102. Asdescribed in greater detail below with respect to FIGS. 6 and 7, theexternal storage device 166 may still be able to communicate with amobile electronic device 102 even when the external storage device 166is in the sleep mode. A mobile electronic device 102 may provide anotification or indication to the external storage device 166 that themobile electronic device 102 would like to, e.g., transfer a file to orfrom the external storage device 168. The notification or indication maybe provided to the wireless communication interface 188 using anappropriate communications protocol for the low-power mode. The wirelesscommunication interface 188 (or a separate microcontroller incommunication therewith, such as a low-power microcontroller) may thencause the primary controller 184 and/or other components of the externalstorage device 166 to “wake up” or otherwise resume normal operations sothat the mobile electronic device 102 can transfer files to or from theexternal storage device 166. The file transfers may then be conductedusing the normal-power mode of the wireless communication interface 188.

In some embodiments, an external storage device 166 may include multiple(e.g., two or more) distinct wireless communication interfaces, ratherthan a single multi-mode wireless communication interface 188. Forexample, one wireless communication interface may be a low-powermicrocontroller (“MCU”) with integrated low-power wireless communicationcapabilities, such as BLE, or which otherwise has access to low-powerwireless communication capabilities. A second wireless communicationinterface may be exclusively or primarily a normal-power communicationinterface, such as a wireless communication interface integrated with orotherwise utilized by the main or primary controller 184 of the externalstorage device 166. The low-power communication interface can managecommunications with mobile electronic devices 102 (or other electronicdevices) while the primary controller 184 and/or other components of theexternal storage device 166 are in sleep mode. The low-powercommunication interface can then cause the primary controller 184 and/orother components of the external storage device 166 to wake up andcommunicate with mobile electronic devices 102 via the normal-powercommunication interface.

The external storage device 166 can include a user interface 190, whichcan be similar to the user interface 118 discussed in connection withthe case 100. The user interface 190 can be configured to receive inputfrom a user (e.g., a command to transfer electrical power, such as viathe power output interface 176, or a command to indicate am amount ofcharge for the battery 172. The user interface 190 can outputinformation to the user (e.g., the amount of charge remaining for thebattery).

The external storage device 166 can include a file management system168, which can have one or more of the features disclosed in connectionwith the file management system 138. For example, the external storagedevice 166 can include a file sharing element, which can be similar to,or the same as, the file sharing element 160 disclosed in connectionwith the device 102. The disclosure relating to the file sharing element160 is applicable to the files sharing element of the external storagedevice 166 and is not repeated here for sake of brevity. The externalstorage device 166 can provide links to files stored in the memory 186to the device 102 and/or to other devices. The external storage device166 can receive requests associated with the provided links and canshare, or otherwise provide access to, files that are related to therequests (e.g., similar to the discussion herein relating to the filesharing element 160. The external storage device 166 can be configuredto host requested files and provide data (e.g., image and/or audioinformation) associated with the hosted files, as discussed herein. Insome embodiments, the file sharing element of the external storagedevice 166 can share a single file with multiple external devices (e.g.,multi-user streaming).

In some embodiments, the file sharing element of the external storagedevice 166 can be configured to translate files stored in the memory 186to a different format (e.g., to be compatible with the mobile electronicdevice 102, or other receiving device), similar to the discussion abovein connection with the file sharing element 160. In some embodiments,the receiving device can perform the format conversion. In someembodiments, the external storage device 166 can be configured toprovide and/or store data in a platform-generic format, similar to thediscussion above in connection with the file management system 138.

In some embodiments, a local server 152 (e.g., on the mobile electronicdevice 102 or on the external storage device 166) can be used to presentfiles that are stored on the memory 186 of the external storage device166 to the media player 148 of the mobile electronic device 102, similarto the discussion above.

FIG. 4A shows various features of an example embodiment of the case 100.FIG. 4B shows various features of another example embodiment of the case100. Electrical power can be delivered to the battery 108 from the powerinput interface 110 (e.g., when the power input interface 110 is coupledto a power source). The electrical power can be routed through a batterymanagement system, which can be configured to route electrical power(e.g., received from the power input interface 110) to the case battery108 and/or to the power output interface 112 (e.g., for relaying theelectrical power to the mobile electronic device 102 (e.g., forrecharging the battery 114). Electrical power from the battery 108 canbe directed (e.g., by the battery management system) to the power outputinterface 112 (e.g., for recharging the battery 114 of the mobileelectronic device 102). Data can be communicated between the power inputinterface 110, the power output interface 112, the controller 120, andthe memory 122. Data can be communicated between the power inputinterface 110 and the power output interface 112, which can enable anexternal device, such as a computer that is coupled to the power inputinterface and the mobile electronic device 102 that is coupled to thepower output interface 112 to communicate with each other. Data can becommunicated between the power input element 110 and the components ofthe case 100 (e.g., the memory 122 and the controller 120), which canenable the case and an external device (e.g., a computer) attached tothe power input interface to communicate with each other. Data can alsobe communicated between the power output interface 112 and thecomponents of the case 100 (e.g., the memory 122 and the controller120), which can enable the case 100 and the mobile electronic device 102to communicate with each other. Many variations are possible.

In some embodiments, a first type of wireless communication (e.g., NFC)can be used to establish a connection or authorization between twodevices, and a second type of wireless communication (e.g., WiFi) can beused to transfer files and other data between the two devices. The firsttype of wireless communication can have a shorter range than the secondtype of wireless communication. For example, NFC can have a relativelyshort range of communication (e.g., generally only a few centimeters),thus NFC communication can be used to establish authorization to sharefiles between two devices. Because NFC communication generally requiresthat the two devices be placed in very close proximity to each other(e.g., touching), the use of NFC to establish sharing authorization canreduce the chance that sharing authorization is unintentionally providedto a device. However, because NFC has a relatively short range, adifferent type of wireless communication (e.g., WiFi or Bluetooth, etc.)can be used to transfer files and data between the two devices, therebyenabling file sharing between authorized devices when they are outsidethe range of NFC.

By way of example, the external device 162 can be brought into closeenough proximity of the mobile electronic device 102 for an NFCconnection between the devices 102 and 162. The file management system138 can store an indication that the external device 162 is authorizedfor file sharing. Files 140 and/or 142 can then be shared with theexternal device 162 (e.g., via a different type of wirelesscommunication such as WiFi, Bluetooth, etc.). In some cases, theexternal device 162 can store an indication that the mobile electronicdevice 102 is authorized for sharing, and the external device 162 canshare files with the device 102 (e.g., via WiFi). By way of anotherexample, the mobile electronic device 102 can be brought into closeenough proximity to the external storage device 166 to establish an NFCconnection between the mobile electronic device 102 and the externalstorage device 166. The mobile electronic device 102 and/or the externalstorage device 166 can store an indication that the other device isauthorized for file sharing, and files can be shared via a differentnon-NFC wireless communication protocol. In some embodiments a userinterface can enable the user to specify the files that are authorizedfor sharing. In some embodiments, the authorization can last for anamount of time and can expire. In some embodiments, multiple devices canhave file sharing authorization at the same time.

With reference again to FIG. 2A, the file management system 138 caninclude a file searching element 192. The searching element 192 can beconfigured to search for files that are located on the device memory134, on the case memory 122, on an external computing device 162, and/oron an external storage device 166. The search element 192 can receive aquery, which can include text. The query can be inputted by a user(e.g., via the touchscreen display 124, via the user input elements, viaa voice command, etc.). The search element 192 can be configured toparse the query and identify parts of the query that relate to differentcategories of data, and the search element 192 can perform the searchbased on the different portions of the query that relate to differentcategories of data. Fuzzy logic, natural language understanding, andother such techniques can be used to parse a query. For example, thesearch can be based on one or more of the following categories of data:file/notification type, action type, time information, geographiclocation information, and user activity information. The searching caninclude searching the metadata of files to identify files that fit thequery. For example, the query “show me all text messages I receivedwhile driving yesterday” can be parsed into various components. Thefile/notification type can be “text messages.” The action type can be“received.” The time information can be “yesterday.” The user activityinformation can be “driving.” The file searching element 192 can thenidentify all the files that satisfy the query (e.g., by searching themetadata). This example, query could enable a user to quickly identify atext message that was missed while driving even if the user does notknow who it was from or exactly when it was received. By way of anotherexample, the query “show me all photos that I took in Europe last year”can be parsed so that the file/notification type is “photos,” so thatthe action type is “taken,” so that the geographic location informationis “in Europe,” and so that the time information is “last year.”

In some embodiments, the query may include tags that the user would liketo use when searching. For example, as described above with respect toFIG. 2B, a user may take photographs at a graduation party, and may tagthe photos accordingly (e.g., by selecting or creating a “graduationparty” tag before or after taking pictures). When searching for taggeditems, the user may simply search for the tag, or provide other searchterms and options (e.g., dates, times, locations, etc.). The searchingelement 192 can search the device memory 134, case memory 122, memory onan external computing device 162 and/or external storage device 166,etc. for files with tags matching (or substantially matching) thequeried tag.

FIG. 5A shows an example network environment in which files can besearched and shared across multiple (e.g., two or more) devices. Variouscombinations of external storage devices 166 a and 166 b, mobileelectronic devices 102 a and 102 b, and cases 100 can communicate witheach other via one or more communication networks 410 and 420. One orboth of the networks may be a publicly accessible network of linkednetworks, possibly operated by various distinct parties, such as theInternet. In other embodiments, one or both of the networks 410 and 420may include a private network, personal area network, local areanetwork, wide area network, cable network, satellite network, cellulartelephone network, etc. or combination thereof, each with access toand/or from the Internet. For example, network 410 may be a WiFi-basedlocal area network, such as a local area network implemented in a homeor office. The network 410 may be provided by various network computingcomponents, such as routers, wireless access points, and the like. Asanother example, the network 420 may be a mobile device network, such asa fourth-generation (4g) cellular phone network, or the network 420 maybe the Internet.

A user of any of the various devices 166 a, 166 b, 102 a, 102 b, and/or100 may use a file management system, such as one of the file managementsystems described herein, to search for files on any one or more of thevarious devices 166 a, 166 b, 102 a, 102 b, and/or 100. For example, auser of device 102 a may initiate a search query, which may includesearch terms, tags, and/or other search options. A file managementsystem 138 executing on device 102 a may search memory 134 of the device102 a for files that match the terms, tags, and other search options.The file management system 138 may also search for files, on theexternal storage device 166 a, matching the terms, tags, and othersearch options. To perform such a search, the file management system 138on the device 102 a may establish communications with the externalstorage device 166 a via the network 410. The file management system 138can transmit search parameters (search terms, tags, and/or other searchoptions) to the external storage device 166 a, and a file managementsystem 168 executing on the external storage device 166 a can performthe search and return any matching files (or data regarding any matchingfiles) to the device 102 a. In some embodiments, the file managementsystem 138 on the mobile electronic device 102 a may perform the searchfor files on the external storage device 166 a, rather than a separatefile management system 168 on the external storage device 166 a. Forexample, the file management system 138 on the mobile electronic device102 a may have access to information about files on the external storagedevice 166 a obtained via periodic or dynamic synchronization proceduresduring which various devices exchange information about their storedfiles.

The file management system 138 may also use the search parameters tosearch for files on other devices connected to the network 410, such asexternal storage device 166 b, case 100, etc. In addition, the filemanagement system 138 may use the search parameters to search for fileson other devices connected to a different network, such as network 420.As described above, network 410 may be a WiFi-based local area network,such as home or office network. The mobile electronic device 102 a mayuse a different network connection, such as cellular telephone network420 to connect to mobile electronic device 102 b. The mobile electronicdevice 102 a may search for files on the other mobile electronic device102 b in a manner similar to that used to search for files in theexternal storage device 166 a, described above. Illustratively, themobile electronic device 102 a may use both network connectionscurrently, or in response to a single search request.

The file management system 138 may determine which devices to include inthe search based on device grouping configuration information, dynamicdevice discovery, etc. For example, one or more users may define adevice group that includes a specified set of devices, such as thedevices 166 a, 166 b, 102 a, 102 b, and/or 100 shown in FIG. 5A. Themobile device 102 a may then search the memory or other file storage ofeach of those devices (or some subset thereof) in response to searchrequests. In some embodiments, the mobile device 102 a may use a defaultcontact method, such as attempting to contact a device over a local areanetwork first. If that contact method fails, the mobile device 102 a mayuse a secondary contact method, such as attempting to contact the deviceover a cellular telephone network and/or the Internet. In addition, oralternatively, file management system 138 may dynamically discoverdevices on which to search for files. For example, the file managementsystem 138 of mobile electronic device 102 a may determine which devicesare currently accessible via the local area network 410, and maytransmit search queries to those devices. The example search methods andconfigurations described and shown are illustrative only, and are notintended to be limiting. In some embodiments, additional and/oralternative search methods and configurations may be used.

The file management system 138 can present search results from multipledevices seamlessly, such that the user is shielded from the underlyingdevice on which each search result is stored. For example, a user maysearch images tagged with the “graduation party” tag described above.Rather than just searching for images on the user's own device 102 a, oron an external device 166 a to which the user may have stored theimages, the user can instead search for images on any device that isreachable via a network connection. If other users on the same localarea network, or in the same device group configuration, have imagestagged “graduation party” stored on their devices, such images may bereturned to the user searching from device 102 a, even though the userof device 102 a may not have taken the images, tagged the images, knownwhere the images where stored, or even known that the images existedprior to conducting the search.

FIG. 5B shows an illustrative example of seamless cross-device searchingand file sharing. As shown, users 450 and 452 may have mobile electronicdevices 460 and 462 respectively (e.g., mobile electronic devices 102 ordevices in cases 100, described above). The users 460 and 462 may be inclose proximity, such as in a home 400, and may therefore be connectedto the same WiFi-based local area network. In addition, there may be anexternal storage device 464 that is also connected to the local areanetwork. The external storage device 464 or the local area network maybe connected to or in communication with a second network 420, which maybe a cellular telephone network or the Internet. A third user 456 withmobile electronic device 466 may be outside the home 400. The mobileelectronic device 466 of the third user 456 may not be connected to orin direct communication with the local area network of the home 400, butmy instead be connected to or in communication with the network 420.

User 456 may initiate a search for tagged files. Illustratively, theuser 456 may initiate a search for files tagged with the “graduationparty” tag described above. The file management system 138 on the user'sdevice 466 can initiate searching for images within memory of the user'sdevice 466, and also images on devices 460, 462 and 464, even though oneor more of those devices may not necessarily be connected to the samenetwork 420 as the third user's device 466. The file management system138 may present results to the user, and the user may interact with theresults without regard to the particular device on which any given imagefile may be stored. For example, the user 456 may define a slide show ofimages tagged with the “graduation party” tag. The slideshow may includeimages from multiple different devices 460, 462, 464, and/or 466,devices connected to different networks (e.g., the local area network ofthe house 400 and/or a cellular telephone network 420), etc. The user456 may initiate playback of the slide show from outside of the home400, and the mobile electronic device 466 can access image files on oneor more other devices 460, 462, and/or 464 as needed via the cellularphone network 420, the external storage device 464, and the local areanetwork of the home 400. Subsequently, the user 456 may enter the home400 and initiate playback of the slide show. The device 466 may in thiscase access images files on the other devices 460, 462, and/or 464 asneeded via the local area network of the home 400. The slideshow maycontinue to work even if one or both of the other devices 460 and/or 462is no longer in the home 400, as long as the user devices 460 and/or 462is accessible via some other network, such as the cellular network 420.

Although the example described above with respect to FIG. 5B focuses onthe use of seamless cross-device searching and sharing of files, theexample is illustrative only, and is not intended to be limiting. Insome embodiments, a user may search for, access, and share any othertype of file. For example, the third user 456 may define a playlist ofmusic, and individual songs on the playlist may be stored as individualfiles on any number of different computing devices. The user 456 maythen start playback of the playlist on device 466, and music files frommobile devices 460 and 462 and/or external storage device 466 may beaccessed and played on device 466 as needed. In addition, the user 456may initiate playback of the playlist regardless of which networkconnection or connections are currently available to the mobileelectronic device 466 as long as the various other devices 460, 462,and/or 464 are accessible to the device 466 via some network.

In some embodiments, files may be stored only once for all devices 460,462, 464 and/or 466 of a group, even if multiple users have initiatedstorage of their own copies of a given file. For example, the storageprovided by the combination of devices 460, 462, 464 and/or 466 of agiven group may be allocated by a file management system 138 (ormultiple file management systems executing on different devices) on anas-needed basis group-wide, rather than a device-specific, user-specificbasis. Therefore, if first user 450 stores a file on external storagedevice 464 (or some other device, such as mobile electronic device 460),a subsequent user that initiates storage of an identical file willinstead be associated with the file stored by the first user 450. Forexample, the file management system 138 executing on a second user'sdevice 462 may determine whether an identical copy of the file has beenstored on any other device of the group of devices and, if so, the filemanagement system can store metadata indicating the location andidentity of file in lieu of storing a duplicate copy of the file.

In some embodiments, tags may be used to determine which users mayaccess shared files. For example, the first user 450 may store aparticular file on the external storage device 464, but may not wish tohave the file available to any and all users associated with the group.The first user 450 may add a tag to the file (as described above)linking the tag to a particular subset of users, such as a “personal”tag indicating that the file is not to be shared with any other user ordevice (in which case the file may be stored on the user's specificdevice 460 by default), a “public” tag indicating that any user ordevice of the group may access the file, a “home” tag indicating thatonly members of the user's household may access the file, etc.

Returning to FIG. 2A, a search query can also include informationregarding one or more actions to be performed on the results. Forexample, the user can provide input to “delete all contacts that weremodified last week,” and the query can be parsed to have afile/notification type of “contacts,” an action type of “modified,” andtime information of “last week.” The query can also be parsed toidentify that the action to be performed on the identified files is“delete.” The time information can be a specific time, or a range oftimes. The geographic location can be specific location or a moregeneral area. In some embodiments, the file searching element 192 canprovide additional information that is determined to be relevant to thesubmitted query. For example, the user can submit a query of “how was mysleep last night?” The file searching element 192 can parse the queryand provide an appropriate response, such as “You slept for 7 hours andthe score of your sleep was 85%.” The file searching element 192 canaccess an appropriate program for computing the sleep score, or the filesearching element 192 can be configured to make this determinationitself. The file searching element 192 can also provide additionalinformation or questions, such as “would you like to see how well yoursleep compares to the national average?” or “would you like to see howwell your sleep compares to your friends?” The search techniquesdiscussed above can be used for searching files on a computer and forsearching for files on the internet as well.

Various embodiments disclosed herein can relate to wearable computingdevices, such as those discussed in PCT Patent Application No.PCT/US2014/045549, filed Jul. 7, 2014, and titled METHOD AND SYSTEM FORCOMMUNICATIVELY COUPLING A WEARABLE COMPUTER WITH ONE OR MORENON-WEARABLE COMPUTERS, which claims the benefit of U.S. ProvisionalPatent Application No. 61/845,316 (the “'316 Application”), filed Jul.11, 2013, and titled METHOD AND SYSTEM FOR COMMUNICATIVELY COUPLING AWEARABLE COMPUTER WITH ONE OR MORE EXTERNAL COMPUTERS, both of which arehereby incorporated by reference in their entirety and made a part ofthis specification for all that they disclose. As described herein andin the '316 Application, wearable computing devices can be used todetermine user activity information. The mobile electronic device 102and/or the wearable computing device can take action based at least inpart on the determined user activity. For example, if a determination ismade that the user is driving, the user's electronic calendar can beconsulted and the device can present or offer to present drivingdirections to the location of the next appointment in the calendar.

When the determination is made that a user has stopped an activity, themobile electronic device 102 and/or the wearable computing device canprovide the user with a summary of the activity that was stopped. Forexample, if the determination is made that the user was running and hasnow stopped, the device can inform the user with information about therun (e.g., of how far the user ran, the average speed, the improvementover one or more prior runs, a map of the run, etc.). In some instances,the device can make an inquiry to the user of whether the user hascompleted the run or has merely stopped temporarily (e.g., to stretch).By way of another example, when the determination is made that the userwas sleeping and is now awake, the mobile electronic device 102 and/orthe wearable computing device can provide the user with a summary of theuser's sleep (e.g., number of hours, score of the estimated quality ofsleep, etc.). In some instances, the device can make an inquiry to theuser of whether the user is finished sleeping or has only awokentemporarily (e.g., to use the bathroom). In some embodiments, the mobileelectronic device 102 and/or the wearable computing device can stopdelivering notifications to the user, or can change the notifications,during the time that the user is asleep (e.g., as discussed in the '316Application). In some embodiments, when the user wakes up, the mobileelectronic device 102 and/or the wearable computing device can providenotifications to the user that were suppressed while the user wassleeping.

In some embodiments, the activity analysis element 158 can conductanalysis on the activities of the user and can recommend modificationsin the user's behavior. For example, by analyzing the user's sleeppatterns, the activity analysis element 158 can determine that when theuser goes to sleep within less than one hour after finishing a run, theuser's sleep quality is lower than when the user finishes running atleast two hours before going to sleep. The mobile electronic device 102and/or the wearable computing device can provide a recommendation thatthe user's schedule be changed so that the user can go running earlierin order to improve the user's quality of sleep. In some embodiments,the activity analysis can include information from a plurality ofindividuals and in some cases can analyze user activity data on a macroscale. For example, analyzing the user activity data could determinewhat activities are commonly performed during the time prior to a heartattack. In the event that the user activities for an individual userindicate a risk of heart attack, the mobile electronic device 102 and/orthe wearable computing device can provide a notification to the user(e.g., a warning or recommendation to change behavior).

Various embodiments disclosed herein relate to systems and methodsrelating to building automation (e.g., home automation). For example,one or more rooms can include sensors that are configured to sense thepresence of a user in the room. The user can be wearing a wearablecomputing device (e.g., a smartwatch), that can communication wirelesslywith the sensors. In some embodiments, the one or more sensors candetermine whether a user wearing a compatible wearable computing deviceis present. In some embodiments, the mobile electronic device 102 and/orthe wearable computing device is configured to determine a location ofthe user (e.g., by communicating with the one or more sensors in the oneor more rooms). A building automation system can be configured to changeparameters of a room in response to the presence of a user. For example,user preferences can be stored in one or more computer-readable memorydevices, and the building automation system can include a controller(e.g., including one or more computing devices) that is configure toaccess the user's preferences from the one or more memory devices and toimplement changes based on the user preferences. For example, thebuilding automation system can chance the brightness of the lights, thetemperature of the room, the volume of a media device, etc. If multipleusers are present the preferences for a dominant user can be used, orthe preferences of the users can be averaged, or combined using aweighted algorithm.

In some embodiments, the building automation system can be configured tochange parameters of a room based at least in part on the user activityinformation (e.g., determined using the wearable computing device). Forexample, if the user is sleeping, the building automation system canturn the lights in the room down or off, and can turn a media deviceoff, or turn the volume down. By way of another example, if the useractivity is determined to be running on a treadmill, the buildingautomation can lower the temperature of the room. Many variations arepossible.

FIG. 6 shows example interactions and data flows between a mobileelectronic device 102 and an external storage device 166. The mobileelectronic device 102 and external storage device 166 may be similar oridentical in many respects to the mobile electronic device 102 andexternal storage device 166 described above. As shown in FIG. 6, theexternal storage device 166 may have a main or primary controller 184,wireless communication interface 188, and a low-power wirelesscommunication interface 198. The low-power wireless communicationinterface 198 may have an integrated MCU, or it may be in communicationwith a separate low-power MCU (not shown).

The mobile electronic device 102 may also have a wireless communicationinterface 136. Illustratively, the mobile electronic device 102 andexternal storage device 166 may communicate wirelessly using variouswireless standards and protocols. Although the examples described belowfocus on the use of Bluetooth and BLE, these examples are illustrativeonly and are not intended to be limiting. In some embodiments, themobile electronic device 102 and external storage device 166 maycommunicate using other wireless standards, protocols, and technologies,such WiFi, 4G LTE, Bluetooth, ZigBee, Ant, and the like.

The external storage device 166 may be in a low-power or “sleep” state,or it may be in a normal-power or “wake” state, depending upon currentoperating conditions. For example, the default state of the externalstorage device 166 may be the sleep state when it is not providingpower, communications, or other features to mobile electronic devices(or to other computing devices). In this way, the external storagedevice 166 can minimize the use of its battery power. However, eventhough the external storage device 166 may be in the sleep state, thelow-power wireless communication interface 198 may remain active andcapable of communicating with other devices. For example, if thelow-power wireless communication interface 198 is configured tocommunicate using BLE, then it may advertise its availability to nearbyelectronic devices at (1). This advertisement can consume substantiallyless battery power than would be required by the wireless communicationinterface 188 to advertise availability or remain ready forcommunication using classic Bluetooth.

At (2), a nearby mobile electronic device 102 in receipt of such anadvertisement may notify the external storage device 166 that it wouldlike to connect to the external storage device 166 (e.g. open andmaintain a wireless communication channel, rather than exchangeadvertisements, notification, indications, and the like). For example, auser of the mobile electronic device 102 may wish to access data storedon the external storage device 166. The wireless communication interface136 of the mobile electronic device 102 can transmit a request ornotification to the external storage device using the appropriatelow-power protocol.

FIG. 7 is a flow diagram of an illustrative process 700 that may beexecuted by the external storage device 166 to respond to notificationsor requests received from other computing devices while the externalstorage device 166 is in the sleep state. The process may be implementedin a set of executable program instructions stored on a non-transitorycomputer-readable medium. The program instructions can be loaded intomemory (e.g., RAM) and executed by a processor (e.g., the low-power MCUintegrated with or in communication with the low-power communicationinterface 198). In some embodiments, the process 700 may be implementedin hardware, such as an integrated circuit.

At block 702, low-power communication interface 198 can receive acommunication from another computing device, such as the notificationreceived from the mobile electronic device 102 at (2), above.

At block 704, the low-power MCU can activate the main controller 184,wireless communication interface 188, and/or other components of theexternal storage device 166. The activation of the components from thesleep state can occur very quickly, thereby minimizing or reducing anylatency perceived by a user of the mobile electronic device 102 whencompared to communicating with an external storage device 166 that isnot in sleep mode. For example, the activation of the external storagedevice 166 components may take less than about 1.0 second, less thanabout 0.5 seconds, or less than about 0.1 seconds.

At block 706, the main controller 184, wireless communication interface188, and/or other components of the external electronic device 166 canconduct a communication session with the mobile electronic device 102.As shown in FIG. 6, the communication session may include the exchangeof data at (4) between the mobile electronic device 102 and the externalstorage device 166, as described in greater detail above. The exchangeof data may include the transmission or streaming of one or more filesto the mobile electronic device 102 for use, the transmission of one ormore files to the external storage device 166 for storage, or any otherappropriate exchange.

At decision block 708, the low-power MCU can determine whether acommunication timeout has occurred. If so, the process 700 can proceedto block 710, whether the main controller 184 and/or any othercomponents activated in block 704 can return to sleep mode. If notimeout has occurred, the process may return to (or remain in) block706, where the communication session is conducted. In some embodiments,a communication session may be terminated by one or both devices. Insuch cases, the MCU can return the components of the external storagedevice 166 to sleep mode without waiting for a timeout period to pass.

Returning to FIG. 6, the low-power wireless communication interface 198may resume advertising availability at (6) after the main controller184, normal power wireless communication interface 186, and/or othercomponents of the external storage device 166 have resumed sleep mode at(5).

In some embodiments, the low-power wireless communication interface 198may not advertise availability when other components of the externalstorage device 166 are in sleep mode. Instead, the lower-power wirelesscommunication interface 198 may monitor various wireless frequencies orfrequency bands—in a process referred to as “listening”—for requests,advertisements, or other communications from the mobile electronicdevice 102 (or other devices). The wireless communication interface 136of the mobile electronic device 102 can initiate communication with theexternal storage device 166 while the external device 166 is in sleepmode by transmitting a request, notification, or other communication tothe external storage device 166 using the appropriate low-powerprotocol. The wireless communication interface 198 can receive thecommunication and activate the main controller 184, wirelesscommunication interface 188, and/or other components of the externalstorage device 166 in order to conduct a communication session with themobile electronic device 102. Upon completion of the communicationsession, expiration of a timeout period after the last communicationactivity, or in response to some other determination, the maincontroller 184, normal power wireless communication interface 186,and/or other components of the external storage device 166 can resumesleep mode. The low-power wireless communication interface 198 mayresume “listening” for communications.

With reference to FIG. 8, in various embodiments, mobile devices canexchange information with each other. The mobile devices 802, 804, and806 can be cell phones (e.g., smart phones), tablet computers, wearablecomputing devices (e.g., smartwatches or smart bands), protectivebattery cases, external storage devices, or combinations thereof, etc.In some embodiments, wearable computing devices (e.g., smartwatches orsmart bands) can communicate directly with each other (e.g., rather thanto a host device such as a cell phone). The mobile devices 802, 804, and806 can communicate by various wireless communication protocols,including Bluetooth, Bluetooth Low Energy, ZigBee, etc. The mobiledevices 802, 804 and 806 can include features described in connectionwith the case 100, the mobile device 102, the file management system 138(and other features discussed in connection with FIG. 2A), and theexternal storage device 166.

In some embodiments, the mobile devices 802, 804, 806 can include publicdata 810 and private data 812. The mobile devices can be configured toshare the public data 810 more freely than the private data 812. Forexample, in some embodiments, the public data 810 can be shared withoutrestriction (e.g., made available to all devices within thecommunication range). In some embodiments, the private data 812 can berestricted so that it cannot be shared with other devices, or so that itis only shared upon permission received from the user. In someembodiments, the public data 810 can be restricted to some degree aswell. For example, the public data 810 can be shared only to approveddevices, such as devices that the user has put onto an approved devicelist, or devices belonging to Facebook friends of the user. The mobiledevices 802, 804, 806 can have several tiers of data with varying levelsof restriction that are customizable by the user, although FIG. 8 onlyshows public data 810 and private data 812.

By way of example, the public data 810 of mobile device 802 can includethe user's name and a link to the user's social medial (e.g., Facebook)profile. The private data 812 can include the photos, videos, calendarappointments, contacts, etc. The mobile device 802 can be configured toshare the public data 810 only with devices on an approved list (e.g.,specified previously by the user of device 802). Thus, device 802 can beconfigured to share the public data 810 with approved mobile device 804(e.g., automatically when devices 802 and 804 are close enough forcommunication), and the device 802 can be configured to not share thepublic data 810 with unapproved mobile device 806.

The devices 802, 804, 806 can store data received from other devices,and the devices 802, 804, and 806, can store data associated with theinteraction between devices (e.g., the identity of the other device oruser, the time that the devices started the interaction, the time thedevices stopped the interaction, and/or the duration of theinteraction). Thus, when devices 802 and 804 come into communicationproximity with each other, each device 802 and 804 can store thatinteraction time, and when the devices 802 and 804 move out ofcommunication proximity, each device 802 and 804 can store that time aswell. This information can be used by a searching element (e.g., similarto or the same as file searching element 192). For example, a user cansubmit a query such as, “who did I see last week while I was jogging,”“who was at the party last night,” or “how long did I see Mikeyesterday.” As discussed herein, the searching element can parse thequery and can identify different categories of data (e.g., time: “lastweek,” activity: “jogging,”). The searching element can use the storeddata to determine who the user interacted with and when.

In some embodiments, a user interface can allow a user to enable ordisable sharing of data (e.g., even public data 810 that would otherwisebe shared). The user interface can allow a user to enable or disablereceiving of data (e.g., even public data broadcast by other devices).

With reference to FIG. 9, in some embodiments, charging devices 904,906, and 908 having supplemental batteries 910 can share informationregarding the available battery power of the supplemental batteries 910.In the example embodiment of FIG. 9, charging device 904 can be abattery case (e.g., battery case 100 discussed herein) coupled to themobile device 902, and charging devices 906 and 908 can be externalstorage devices (e.g., external storage devices 166 discussed herein).The information can be communicated using various wireless communicationprotocols, including Bluetooth, Bluetooth Low Energy, ZigBee, etc. Insome embodiments, the battery information can be transferred from thecharging device 904 to the mobile device 902 via a wired connection(e.g., if the mobile device is mounted in a battery case charging device904). In some embodiments, an external charging device 906 cancommunicate the battery information to the mobile device 902 directly,or relayed through the charging device 904 that is coupled to the mobiledevice 902.

In some embodiments, the charging devices 904, 906, 908 can provide thebattery information in response to a request received from anotherdevice (e.g., from the mobile device 902, such as a cell phone, tabletcomputer, etc.). For example, a user can send a query from the mobiledevice 902 requesting information about available battery power. In theexample of FIG. 9, the charging device 904 belongs to the user and is abattery case 100 coupled to the mobile device 902, the charging device906 belongs to the user and is an external storage device 166 (e.g., inthe user's backpack). The charging device 908 belongs to a differentuser and is within the wireless communication range. In someembodiments, the charging devices 904, 906, 908 can share the batteryinformation only with approved devices. For example, the mobile device902 can request battery information only from devices that are on a listof devices owned by the same user (e.g., charging devices 904 and 906).In some embodiments, the mobile device 902 can request batteryinformation from all available sources (e.g., charging devices owned bythe same user, charging devices owned by other users within thecommunication range, charging devices that are for sale or available forpublic use within the communication range). The battery information canbe categorized and displayed on the mobile device 902. For example, adisplay can show the amount of battery power available on chargingdevices that belong to the user, on charging devices owned by othernearby users, on charging devices for sale nearby, etc.). In someembodiments, charging devices can transmit location information (e.g.,GPS coordinates) to a mobile device 902 to help the user of the mobiledevice to find the charging device 906. The mobile device 902 candisplay a map showing the locations of available charging devices. Thecharging devices can include a user interface to allow a user to enableor disable the sharing of battery information from the charging devices,or to configure the parameters and restrictions of battery informationsharing.

In some embodiments, the mobile device 902 can provide information abouthow long it will take for the battery of the mobile device 902 to becomefully charged, for example, based on one or more of the current onto thebattery, the current off of the battery, a battery charge decayalgorithm, and a voltage output from the battery.

With reference to FIG. 10, in some embodiments, a mobile device 1002 cancommunicate wirelessly with sensor systems 1004 a-d to gatherinformation. For simplicity the components of the sensor systems 1004a-d are shown in connection with sensor system 1004 a, and the othersensor systems 1004 b-d can include similar components. The sensorsystem 1004 a can include one or more sensors 1006 (e.g., a temperaturesensor, a humidity sensor, a light sensor, a microphone, etc.). Thesensor system 1004 a can include a communication interface 1008configured to communicate with the mobile device 1002 and/or with othersensor systems 1004 b-d by a wireless communication protocol (e.g.,Bluetooth, Bluetooth Low Energy, Wifi, ZigBee, etc.). In someembodiments, Bluetooth Low Energy can be used because of its low powerconsumption. The sensor system 1004 a can include a controller 1010configured to operate the components of the sensor system 1004 a asdiscussed herein. The sensor system 1004 a can include memory 1012,which can store information collected by the one or more sensors 1006.In some embodiments, the memory 1012 can store the information from asensor 1006 for a time (e.g., one day, two days, four days, one week, ortwo weeks, etc.), and after that time, the controller 1010 can calculateaverage values to be stored in the memory 1012 (e.g., daily averages,weekly averages, etc.). The sensor system 1004 a can include a battery1014 to provide power to the components of the sensor system 1004 a. Thesensor system 1004 a can be configured to consume very little power suchthat a small battery (e.g., a button cell battery) can operate thesensor system 1004 a for extended periods of time (e.g., days, months,or years).

The sensor systems 1004 a-d can be configured to send information to amobile device 1002 in response to a query sent by the mobile device1002. For example, a user can use the mobile device 1002 to send a queryasking for temperature information. A sensor system 1004 a-d having atemperature sensor that is within communication range can sendtemperature information to the mobile device in response to the query.The mobile device 1002 can request past information (e.g., what was thetemperature at this location 2 hours ago, or yesterday, or last week).The sensor system 1004 a-d can access past information from the memoryand send the information to the mobile device 1002.

In some embodiments, information can be relayed from one sensor system1004 d to another 1004 c. In the embodiment of FIG. 10, the mobiledevice 1002 is within the communication range of sensor system 1004 c,but not 1004 d. Information from sensor system 1004 d can be sent tosensor system 1004 c, which can send the information to the mobiledevice 1002. By way of example, mobile device 1002 can request humidityinformation. If the sensor systems 1004 a-c that are within directcommunication range of the mobile device 1002 cannot provide therequested humidity information, the sensor systems 1004 a-c can relaythe request to other sensor systems 1004 d that are out of directcommunication range with the mobile device 1002. In FIG. 10, sensorsystem 1004 c (e.g., which can include a temperature sensor) can relaythe request for humidity information to the sensor system 1004 d (whichcan include a humidity sensor). The sensor system 1004 d can send therequested humidity information to the sensor system 1004 c, and thesensor system 1004 c can send the requested humidity information to themobile device 1004 b. In some embodiments, the memory 1012 of the sensorsystem can store information about the other surrounding sensor systemsso that the sensor systems 1004 a-d can appropriately direct queries toother sensor systems 1004 a-d.

Sensor systems 1004 a-d can be used in connection with buildingautomation systems (e.g., home automation systems). As discussed above,sensors can detect the presence of a user in a room. Sensor systems 1004a-d can be used to detect environmental information as discussed herein(e.g., temperature, humidity, light levels, sound volume). An automationcontroller can change parameters based on the user presence informationand/or the environmental information. The automation controller can usevarious different communication protocols. For example, a relativelyshort-range communication protocol (e.g., Bluetooth or Bluetooth LowEnergy) can be used by the automation controller to communicate withsensor systems 1004 a-d and devices within short ranges. A longer-rangecommunication protocol (e.g., Wifi) can be used to communicate withsensor systems 1004 a-d and devices at longer ranges. In someembodiments, the automation controller can include, or be incommunication with, a router (e.g., 4G router) which can enablecommunication with remote devices. In some embodiments, the automationcontroller can communicate with remove devices via the internet.

In some embodiments, content providing devices can be used to downloadcontent (e.g., videos). For example, videos and other content can bedownloaded by a cell phone, a tablet computer, a laptop, a personalcomputer, a smart TV, a DVR system, etc. In some instances, a user mustwait for the video to at least partially download before the user canbegin to watch the video. In some embodiments, a content providingdevice can predict videos and/or other content that a user is likely towant and can pre-download that content before the user has requested toview the content. Thus, if the user later requests to view thepre-downloaded content, the user can view the content without waitingfor the content to be downloaded. By way of example, if a user requeststo watch one episode of a show, the content providing device can alsodownload one or more of the subsequent episodes of that show. In someembodiments, the pre-downloaded content can be stored in a restricted(e.g., encrypted) manner so that the user cannot view the pre-downloadedcontent until that content is paid for.

One or more of the features illustrated in the drawings and/or describedherein may be rearranged and/or combined into a single component orembodied in several components. Additional components may also be added.While certain example embodiments have been described and shown in theaccompanying drawings, it is to be understood that such embodiments aremerely illustrative of and not restrictive. Thus, the inventions are notlimited to the specific constructions and arrangements shown anddescribed, since various other modifications may occur to thoseordinarily skilled in the art based on the present disclosure.

The various operations of methods described above may be performed byany suitable means capable of performing the operations, such as varioushardware and/or software component(s), circuits, and/or module(s).Generally, any operations illustrated in the Figures may be performed bycorresponding functional means capable of performing the operations.

The methods disclosed herein comprise one or more steps or actions forachieving the described method. The method steps and/or actions may beinterchanged with one another without departing from the scope of theclaims. In other words, unless a specific order of steps or actions isspecified, the order and/or use of specific steps and/or actions may bemodified without departing from the scope of the claims. Method stepand/or actions disclosed herein can be performed in conjunction witheach other, and steps and/or actions can be further divided intoadditional steps and/or actions.

The various illustrative logical blocks, modules and circuits describedin connection with the present disclosure may be implemented orperformed with a general purpose processor, a digital signal processor(DSP), an application specific integrated circuit (ASIC), a fieldprogrammable gate array signal (FPGA), or other programmable logicdevice (PLD), discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. A general purpose processor may be a microprocessor,but in the alternative, the processor may be any commercially availableprocessor, controller, microcontroller, or state machine, etc. Aprocessor may also be implemented as a combination of computing devices,e.g., a combination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration.

In one or more aspects, the functions described may be implemented inhardware, software, firmware, or any combination thereof. If implementedin software, the functions may be stored on or transmitted over as oneor more instructions or code on a computer-readable medium.Computer-readable media includes both computer storage media andcommunication media including any medium that facilitates transfer of acomputer program from one place to another. A storage media may be anyavailable media that can be accessed by a computer. By way of example,and not limitation, such computer-readable media can comprise RAM, ROM,EEPROM, CD-ROM, or other optical disk storage, magnetic disk storage orother magnetic storage devices, or any other medium that can be used tocarry or store desired program code in the form of instructions or datastructures and that can be accessed by a computer. Also, any connectionis properly termed a computer-readable medium. For example, if thesoftware is transmitted from a website, server, or other remote sourceusing a coaxial cable, fiber optic cable, twisted pair, digitalsubscriber line (DSL), or wireless technologies such as infrared, radio,and microwave, then the coaxial cable, fiber optic cable, twisted pair,DSL, or wireless technologies such as infrared, radio, and microwave areincluded in the definition of medium. Disk and disc, as used herein,includes compact disc (CD), laser disc, optical disc, digital versatiledisc (DVD), floppy disk and blu-ray disc where disks usually reproducedata magnetically, while discs reproduce data optically with lasers.Thus, in some aspects computer readable medium may comprisenon-transitory computer readable medium (e.g., tangible media). Inaddition, in some aspects computer readable medium may comprisetransitory computer readable medium (e.g., a signal). Combinations ofthe above should also be included within the scope of computer-readablemedia.

It is to be understood that the claims are not limited to the preciseconfiguration and components illustrated above. Various modifications,changes and variations may be made in the arrangement, operation anddetails of the methods and apparatus described above.

The following is claimed:
 1. A system comprising: a case configured toreceive a mobile electronic device, the case comprising: a top wall; abottom wall; a power output interface coupled to the bottom wall, thepower output interface configured to engage a power input interface ofthe mobile electronic device, wherein the top wall is movable withrespect to the power output interface from a first position in which thecase is permitted to be removably attached to the mobile electronicdevice to a second position in which detachment of the case from themobile electronic device is inhibited by engagement of the power outputinterface with the power input interface; a battery, wherein the poweroutput interface is configured to convey electrical power from thebattery; an indicator component configured to indicate an amount ofpower in the battery; and a non-transitory computer-readable case memoryconfigured to store data accessible by at least the mobile electronicdevice via the power output interface; and a non-transitory computerreadable medium having stored thereon a file management systemconfigured to run on the mobile electronic device, the file managementsystem configured to at least: provide, to a media player executing onthe mobile electronic device, access to a first media file in the casememory using a server-based communication protocol; and provide, to themedia player, access to a second media file in memory of the mobileelectronic device using a local storage access protocol.
 2. The systemof claim 1, wherein the file management system is further configured toat least cause the mobile electronic device to transmit the media fileto a second mobile electronic device via a wireless communicationchannel.
 3. The system of claim 1, wherein the file management system isfurther configured to store metadata in connection with the first mediafile, the metadata comprising a tag defined by a user.
 4. The system ofclaim 3, wherein the tag comprises an audio recording.
 5. A systemcomprising: a case configured to removably attach to a mobile electronicdevice, the case comprising: a battery; a non-transitorycomputer-readable case memory; and an output interface configured to atleast: engage an input interface of the mobile electronic device; conveyelectrical power from the battery to the input interface of the mobileelectronic device; and provide the mobile electronic device access todata stored in the case memory; and a non-transitory computer readablemedium having stored thereon a file management system configured to runon the mobile electronic device, the file management system configuredto at least provide, to an application executing on the mobileelectronic device, access to data in the case memory.
 6. A combinationof the system of claim 5 and the mobile electronic device.
 7. The systemof claim 5, wherein the file management system is configured to provideaccess to the data in the case memory using a server-based communicationprotocol.
 8. The system of claim 5, wherein the file management systemis further configured to at least cause the mobile electronic device totransmit the data stored in the case memory to a second mobileelectronic device via a wireless communication channel.
 9. The system ofclaim 5, wherein the file management system is further configured to atleast provide access to data in memory of the mobile electronic deviceusing a local storage access protocol.
 10. The system of claim 5,wherein the file management system is further configured to at leaststore metadata in connection with a file stored in the case memory. 11.The system of claim 10, wherein the metadata comprises a tag defined bya user.
 12. The system of claim 10, wherein the metadata comprises a taggenerated based at least partly on calendar data stored in memory of themobile electronic device.
 13. The system of claim 5, wherein the filemanagement system is further configured to provide access to a filestored in the case memory by transmitting, to a remote electronicdevice, a link to the file stored in the case memory.
 14. The system ofclaim 5, wherein the file management system is further configured to atleast search a plurality of mobile electronic devices for a file meetinguser-supplied search criteria.
 15. The system of claim 14, wherein thefile management system is further configured to search the plurality ofmobile electronic devices using at least two different networkconnections in response to a single search request.
 16. The system ofclaim 14, wherein the file management system is further configured tosearch the plurality of mobile electronic devices by communicating withfile management systems executing on the plurality of mobile electronicdevices.
 17. The system of claim 14, wherein the file management systemis further configured to at least enable modification of a search resultfile stored on a remote mobile electronic device of the plurality ofmobile electronic devices.
 18. The system of claim 5, wherein the filemanagement system is further configured to at least enable presentationof a sequence of two or more media files, wherein at least a first mediafile of the two or more media files is retrieved from a first remotemobile electronic device, and wherein at least a second media file ofthe two or more media files is retrieved from a second remote mobileelectronic device.
 19. The system of claim 18, wherein the sequence oftwo or more media files comprises a playlist of audio files or a slideshow of image files.
 20. The system of claim 5, wherein the filemanagement system is configured to search for a file based at least inpart on user activity information.
 21. The system of claim 20, whereinthe user activity information comprises an indication of an activitythat the user was performing when the file was created or modified. 22.A method of manufacturing a case, the method comprising: providing ahousing configured to removably attach to a mobile electronic device,the housing comprising a battery and a non-transitory computer-readablecase memory; providing an output interface configured to engage an inputinterface of the mobile electronic device, wherein the output interfaceis further configured to convey electrical power from the battery to ainput interface, and wherein the output interface is further configuredto provide access to data stored in the case memory; attaching theoutput interface to the housing; and providing a non-transitory computerreadable medium having stored thereon a file management systemconfigured to run on the mobile electronic device, the file managementsystem configured to at least provide, to an application executing onthe mobile electronic device, access to data in the case memory.
 23. Anelectronic storage device comprising: a first wireless communicationinterface; a second wireless communication interface configured toconsume less power than the first wireless communication interfaceduring operation; and a computing device configured to at least:transmit, using the second wireless communication interface, indicatorsregarding availability of the electronic storage device; receive, usingthe second wireless communication interface, a communication from amobile electronic device; and in response to the communication: activatethe first wireless communication interface, wherein the electronicstorage device transmits data to the mobile electronic device using thefirst wireless communication interface subsequent to activation of thefirst wireless communication interface; and subsequent to transmittingthe data to the mobile electronic device using the first wirelesscommunication interface, deactivate the first wireless communicationinterface.